Provisioning of virtual machines using an N-ARY tree of clusters of nodes

ABSTRACT

Various systems and methods for management and provisioning of virtual machines are disclosed. This invention may be used, e.g., in conjunction with clusters of nodes that are potentially capable of hosting one or more virtual machines. In one aspect of this invention, the nodes may rank themselves, or be ranked, based on their ability to support a requested virtual machine configuration. Each of the clusters may also be ranked based on, for example, the aggregate ranks of the nodes within that cluster. After the nodes and/or clusters have been ranked, a cluster and/or a node may be selected to host the virtual machine, and the virtual machine may be provisioned on that cluster and/or node.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application is a continuation of U.S. patent application Ser. No. 13/327,218, filed on Dec. 15, 2011, entitled “MANAGEMENT AND PROVISIONING OF VIRTUAL MACHINES,” and is incorporated by reference herein in its entirety and for all purposes.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This application relates to management and provisioning of virtual machines. Particularly, this application relates to managing virtual machine configuration and provisioning of virtual machines based on such virtual machine configuration.

2. Description of the Related Art

A distributed computing system can include multiple computing nodes (nodes) that communicate with and access, using a network, data stored on a shared storage device. Each such node can implement multiple virtual machines that allow increased usage of hardware resources, i.e., by using the hardware resources of each node to support multiple virtual machines. Each virtual machine (VM) can execute a separate operating system, and can be interacted with, and used in substantially the same manner as, a standalone operating system executing on independent hardware. It is desirable to be able to determine the resource needs of virtual machines, when configuring a node to host the virtual machine.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the present application may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

FIG. 1 is a block diagram illustrating a cluster that includes a collection of nodes and storage, according to one embodiment.

FIGS. 2A and 2B are a blocks diagram illustrating communication between an administrator module and configuration information, according to one embodiment.

FIG. 3 is a block diagram illustrating various components of a virtual machine configuration, according to one embodiment.

FIG. 4 is a flowchart illustrating a method for management and provisioning of virtual machines, according to one embodiment.

FIG. 5 is a flowchart illustrating a method for providing a virtual machine at a node of a cluster selected using virtual machine configuration, according to one embodiment.

FIG. 6 is a flowchart illustrating a method for selecting a cluster and/or a node using virtual machine configuration, according to one embodiment.

FIG. 7 is another block diagram illustrating a cluster that includes a collection of nodes and storage, according to one embodiment.

FIG. 8 is another block diagram illustrating an administrator module, according to one embodiment.

FIG. 9 is a block diagram illustrating various components of a cluster configuration, according to one embodiment.

FIG. 10 is another block diagram illustrating various components of a cluster configuration, according to one embodiment.

FIG. 11 is a block diagram illustrating a notification system including a notification infrastructure and notification modules, according to one embodiment

FIG. 12 is a flowchart illustrating a method for performing an action based on operational indicators of a cluster/node where a virtual machine is provisioned, according to one embodiment.

FIG. 13 is a flowchart illustrating a method for comparing virtual machine configuration to operational indicators of a cluster/node where a virtual machine is provisioned, according to one embodiment.

FIG. 14 is a block diagram illustrating several clusters that include a collection of nodes and storage, according to one embodiment.

FIG. 15 is a diagram illustrating an example of a n-ary tree that can be used when comparing virtual machine configuration to operational indicators of a cluster/node where a virtual machine is provisioned, according to one embodiment.

FIG. 16 is a flowchart illustrating a method for selecting a cluster for hosting a virtual machine, according to one embodiment.

FIG. 17 is a flowchart illustrating a method for generating an n-tree when selecting a cluster and/or a node using virtual machine configuration, according to one embodiment.

FIG. 18 is another flowchart illustrating a method for generating an n-tree when selecting a cluster and/or a node using virtual machine configuration, according to one embodiment.

FIG. 19 is a block diagram illustrating a network architecture in which embodiments of the present application can be implemented.

FIG. 20 is a block diagram that illustrates an example of a computer system suitable for implementing embodiments of the present application.

While the embodiments of the application are susceptible to various modifications and alternative forms, specific embodiments are provided as examples in the drawings and detailed description. It should be understood that the drawings and detailed description are not intended to limit the embodiments to the particular form disclosed. Instead, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the invention as defined by the appended claims.

DETAILED DESCRIPTION

Although the present invention has been described in connection with several embodiments, the invention is not intended to be limited to the specific forms set forth herein. On the contrary, it is intended to cover such alternatives, modifications, and equivalents as can be reasonably included within the scope of the invention as defined by the appended claims.

Embodiments of the present invention are directed to managing virtual machine (VM) configuration. Such VM configurations are associated both with VMs that are to be provisioned on (and so be hosted on) a node, as well with VMs that are already being hosted by such nodes. A VM configuration can include one or more resource requirements as well as one or more additional requirements. Resource requirements indicate one or more resources that are needed in a node for hosting this VM. Additional requirements indicate one or more operational elements needed in a node for hosting this VM. This VM configuration is compared to configurations of various clusters. The cluster configuration can indicate configuration information for node(s) of that cluster. This comparison can be used to select a cluster that includes nodes that can meet the resource and the additional requirements for hosting this VM.

FIG. 1 is a block diagram illustrating a cluster 100 that includes a collection of nodes and storage. Cluster, e.g., cluster 100, includes several nodes, e.g., nodes 102A, 102B, and 103C. Each node can communicate with storage, e.g., storage 104, using a network, e.g., network 106. Although only three nodes 102A-102C are shown, cluster 100 may include a different number of nodes. Each such node can implement one or more virtual machines, e.g., virtual machines 108A-108C. In some embodiments, each node may implement virtual machines using hypervisor technology, although other architectures are contemplated.

A VM can be provisioned based on a service level agreement (SLA) associated with that VM. An SLA can include various resource requirements such as physical requirements of a node where that VM is provisioned. These resource requirements can include CPU, memory, and other hardware requirements. As a result, the VM is provisioned on a server that has the resources specified by the resource requirements of the SLA associated with that VM.

In one embodiment, the cluster can have associated cluster configuration, e.g., cluster configuration 110. Cluster configuration can include configuration information for the cluster and/or configuration information for node(s). For example, cluster information 110 can include configuration information 110A for node 102A and configuration information 110B for node 102B. A detailed description of such configuration information is provided in connection with the examples presented in FIG. 3. It is noted that while FIG. 1 shows a single node (node C 102C) supporting such cluster configuration, this is made for illustrative purposes only, and cluster configuration 110 can be supported, implemented, accessed, and/or stored anywhere in cluster 100. For example, cluster configuration 110 can be distributed among nodes 102A and 102B of cluster 100, and/or storage 104. Cluster configuration can also be stored outside cluster 100, such as at a central repository, and be accessed via network 106, as desired.

VM configuration, such as VM configuration 112, includes resource requirement(s), and one or more additional requirement(s). It is noted that while FIG. 1 shows a single node (node C 102C) supporting such VM configuration, this is made for illustrative purposes only, and VM configuration 112 can be supported, implemented, accessed, and/or stored anywhere in cluster 100. For example, VM configuration 112 can be distributed among nodes 102A and 102B of cluster 100, and/or storage 104. VM configuration can also be stored outside cluster 100, such as at a central repository, and be accessed via network 106, as desired. In one embodiment, the VM configuration is included in the VM's service level agreement (SLA). In one embodiment, the VM configuration is associated with a VM that is not yet hosted. For example, a command can be received requesting a creation of a new VM (e.g., to be provisioned at a node) according to the VM configuration. In another embodiment, the VM configuration is associated with a VM that is already being hosted on one of nodes of a cluster. For example, a command can be received requesting that a VM be provisioned at a new node according to the VM configuration.

An SLA can include VM configuration, such as both resource requirements and additional requirements. Resource requirements such as physical requirements of a node where this VM can be provisioned. These resource requirements can include CPU, memory, and/or other hardware requirements. The resource requirement(s) indicate resource(s) needed in a node for hosting the VM. For example, these resources include various hardware requirements of a node for hosting the VM. As a result, the VM can be provisioned on a node that has the resources specified by the resource requirements of the SLA associated with this VM.

The additional requirements indicate operational element(s) needed in a node for hosting the VM. For example, these additional requirements can include availability requirements, data protection requirements, and security requirements, among others. The availability requirements can define the VM's availability requirement(s). The data protection requirement(s) can indicate data protection elements needed in a potential node for hosting the VM. The security requirement(s) can indicate security elements needed in the potential node for hosting the VM. The operation element(s) can indicate data protection elements needed in a potential node for hosting the VM.

In one embodiment, node(s) in the cluster includes an administrator module, e.g., administrator module 114. It is noted that while FIG. 1 shows a single node (node 102C) supporting such administrator module, which is done for illustrative purposes only. Such as administrator module 114 can be implemented, executed, and/or stored anywhere in cluster 100. For example, administrator module 114 can be distributed among nodes 102A and 102B of cluster 100, and/or storage 104. In one embodiment, one or more agents (such as shown in FIG. 7) are used instead of, or in addition to, the administrator module. Administrator module 114 can also be stored outside cluster 100, such as at a central repository, and be accessed via network 106, such as for execution, as desired. It is noted that a cluster, in general terms, is a collection of nodes that are grouped together and can share one or more resources. Typically, a cluster is a collection of nodes that share the same storage system. In one implementation, the nodes of a cluster are managed by the same cluster software. As a result, VMs can be easily provisioned from one node of a cluster to another node on that same cluster. In one implementation, the nodes in a single cluster are connected together, such as by a network, e.g., a Local Area Network (LAN).

In one embodiment, administrator module 114 accesses virtual machine configuration 112 of a virtual machine that is to be provisioned. For example, administrator module 114 (and/or agent(s)) can receive a request that such a VM is to be provisioned at a node at a cluster, as long as this node matches the requirements in the VM configuration associated with this VM. Administrator module 114 (and/or agent(s)) can access cluster configuration 110 of cluster 100. Administrator module 114 (and/or agent(s)) can then compare VM configuration 112 and cluster configuration 110. Administrator module 114 (and/or agent(s)) can also access a cluster configuration of another cluster (not shown). This example illustrates how the administrator node can access cluster configuration of several clusters. Thus, administrator module 114 (and/or agent(s)) can access cluster configuration (not shown) of other clusters.

For example, a second cluster can include several nodes, which can be configured to host at least one VM. Cluster configuration for this second cluster can also include configuration information for these nodes. The administrator module can then compare the VM configuration and the second cluster configuration. The administrator module can determine which cluster from the accessed clusters (e.g., cluster 100 and the second cluster) can best host the VM, such as based on the comparison of the cluster configuration for the accessed clusters. Once the administrator module determines which cluster can host the VM, the administrator module (and/or agent(s)) can then select a node from this selected cluster.

Once the administrator module (and/or agent(s)) selects a node from this selected cluster, the administrator module (and/or agent(s)) can provision the virtual machine at one of the first nodes. In one embodiment, prior to provisioning the VM on the selected node, the administrator module and/or other module can first configure the selected node in accordance with one or more of the additional requirements. For example, the administrator module and/or the other module can configure operational characteristic(s) in the selected node. For example, to comply with the data protection requirement (of VM configuration) for hosting the VM, the administrator module (and/or agent(s)) can configure a certain data protection technique for a node (or for any VMs hosted by this node).

VM configuration 112 can also be stored with VM configurations for the other VMs that are already being hosted (e.g., VM configuration for VMs 108A-108C). The VM configuration can be stored with VM configuration for cluster 100 as well as the other cluster(s). For example, as described below, such stored VM configuration can be used to determine whether nodes that are hosting VMs are maintaining their operation as agreed in the respective SLAs. In one embodiment, VM configuration can be stored for a VM once that VM is provisioned.

FIG. 2A is a block diagram illustrating an administrator module accessing cluster configuration and VM configuration, according to one embodiment. As shown, administrator module 202 includes a provisioning module 204, a comparison module 206, a determination module 208, a configuration module 210, and a selection module 212. It is noted that in some embodiments, the various modules of administrator module 202 may be combined or further divided, and are depicted in FIG. 2A as such, solely for purposes of illustration. Thus, administrator module 202 can include fewer, or additional modules, as desired. Furthermore, in some embodiments, one or more of these modules may be combined. For example, comparison module and determination module can be combined into one module. Still further, various modules of administrator module 202 may be implemented as a single software and/or hardware module, as desired. Administrator module 202 can be an implementation of administrator module 114 of FIG. 1. In one embodiment, agent(s) can implement some, or all, of functionality of the administrator module.

Comparison module 206 is operable to compare VM configuration to cluster configuration, such as cluster configuration 214. In one embodiment, comparison module 206 can access node configuration for each cluster. In this embodiment, comparison module 206 accesses resources and/or operational elements of each such node. In another embodiment, comparison module 206 can access cluster information to access configuration information for nodes (of that cluster). For example, such cluster information can already be created to reflect the resources and/or operational elements for node(s) that are included by that cluster. Comparison module 206 can determine whether the additional requirements (of VM configuration) match the operational elements of nodes for the respective cluster. Determination module 208 is operable to determine a cluster from various clusters that are compared by comparison module 206. Determination module 208 is configured to perform the determination based on a comparison of the VM configuration and cluster configurations for each of the various clusters.

Selection module 212 is configured to select a node from the nodes in the cluster (cluster that was determined by determination module 208). Configuration module 210 is configured to configure this selected node in accordance with the additional requirements. Provisioning module 204 is operable to provision a VM on a node of a cluster, such as node 102A of cluster 100. Provisioning module 204 can provision this VM on a node that is selected (e.g., by selection module 212) on a cluster that is determined (e.g., by determination module 208). In one embodiment, such selected node can first be configured (e.g., by configuration module 210) in accordance with additional requirements of the VM configuration for the VM that is to be provisioned.

In one embodiment, cluster configuration 214 includes configuration information for node(s) included in a respective cluster. For example, cluster configuration 214 that is associated with a cluster (e.g., cluster 100) includes configuration information for nodes 102A and 102B. In one embodiment, cluster information 214 includes separate configuration information for its respective nodes, e.g., node A configuration 214A and node B configuration 214B. In other embodiments, cluster configuration 214 includes configuration information that has already been generated for its nodes. VM configuration 216 can include resource requirement(s) and additional requirement(s) for a VM that is to be provisioned. VM configuration 216 is further described below with reference to FIG. 4. Administrator module 202 can access cluster information 214 and/or VM configuration using a connection 218, which can be a memory bus, software API/function calls, notifications, data messaging, and/or a network, etc., depending on implementation.

For example, FIG. 2B is a block diagram showing one implementation of how various modules of an administrator module (e.g., administrator module 202 of FIG. 2) can access cluster information VM configuration. In one embodiment, various modules of an administrator module (e.g., a provisioning module 204, a comparison module, 206, a determination module 208, a configuration module 210, and a selection module 212) can access cluster information for two clusters (e.g., cluster configuration 214A of a first cluster and/or cluster configuration 214B of a second cluster). In one embodiment, various modules of the administrator module can also/instead access VM configuration 216A for a first VM to be provisioned, and also VM configuration 216B for a second VM to be provisioned. Various modules of the administrator module (and/or agent(s)) can access such cluster configuration and/or VM configuration using an infrastructure 218, which can be a memory bus, software API/function calls, notifications, data messaging, and/or a network, etc., depending on implementation.

FIG. 3 is a block diagram of a VM configuration 302, such as VM configuration described in FIGS. 1-2. VM configuration 302 can include resource requirement(s) 304 and additional requirement(s) 306. Resource requirement(s) 304 can include resource requirement(s) 304A, 304B, . . . 304N. Additional requirement(s) 306 can include additional requirement(s) 306A, 306B, . . . 306M.

Resource requirement(s) 304 can define the VM's various resource requirements. Resource requirements can include CPU, memory, network, platform, IS, boot disk image, etc. These are typically hardware requirements of the node (e.g., a server) for hosting a VM. Additional requirement(s) 306 can include availability requirements, data protection requirements, and security requirements.

Availability requirements can define the VM's availability requirement(s), e.g., the number of physical host failures that the virtual machine needs to be able to tolerate, the number of remote sites configured for the virtual machine's disaster recovery, etc. For example, a requirement could include that a VM needs to tolerate N physical host failures. This requirement can be met by the clusters having at least N+1 physical hosts capable of meeting the VM's resource requirement(s). In another example, a requirement can include a VM tolerating one site failure, i.e., it needs to have a Disaster Recovery setup. This requirement can be met only by the clusters in the data centers that have Disaster Recovery (DR) configured, such as where there is a cluster (e.g., at a remote site) that can be used to activate the virtual machines active on the cluster. For example, a cluster in New York could have a corresponding DR cluster setup in London. If a host in the New York cluster fails, the virtual machines that were active on the cluster in New York can be made available via the DR cluster in London.

Data Protection Requirements define the frequency, media and method/type for the backup or the snapshot of the virtual machine. For example, a requirement may be that an image needs to be backed up every H hours using a particular type of backup software. Another requirement may require use of a certain type of backup, such as incremental or full backup. This requirement can be met by hosts that have appropriate backup software (e.g., NBU, BackupExec) setup and have access to backup media.

Security Requirements define the security zones for the virtual machine to restrict the networks that the virtual machine will have access to, policies and frequency for malware scanning, etc. For example, a requirement may be to scan a VM disk image for virus every N hours. This requirement can be met by setting virus scan software within a VM and/or the node hosting a VM. Alternatively, this requirement can be done offline from wherever VM image is accessible, e.g., where the VM image is placed, or another host that has access to the virtual machine's disk image. In another example, a requirement can be to have a virtual infrastructure be compliant to some guidelines e.g., VMware vSphere guidelines. This requirement can be met by checking the hypervisor, network, storage for compliance with compliance assessment systems such as CCS. Another example of a requirement is that the VM needs to be provisioned on a host that has DLP gateway configured to scan all outbound traffic. This SLA can be met by hosts that have DLP gateway that can be configured to scan all outbound traffic of a VM.

FIG. 4 is a flowchart illustrating a method for management and provisioning of virtual machines, according to one embodiment.

In element 402, a cluster is selected for hosting a VM. For example, a cluster is selected based on VM configuration of a VM. This cluster selection is described in more detail with regard to FIGS. 5 and 16, among others.

In element 404, a node is selected within the selected cluster for hosting the VM. For example, a node is selected within the selected cluster based on the VM configuration. This node selection is also described in more detail with regard to FIGS. 5 and 16, among others.

In element 406, the VM is provisioned on the selected node. For example, the VM is provisioned using the VM configuration. This VM provisioning is also described in more detail with regard to FIGS. 5 and 16, among others.

In element 408, a determination is made whether the node hosting the VM is operating within the operating parameters. If the node hosting the VM is not operating within the operating parameters, then execution of method 400 can start again at element 402. This is described in more detail with regard to FIGS. 12 and 13, among others.

FIG. 5 is a flowchart 500 of a method for management and provisioning of virtual machines, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified by in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 500 is described with reference to variations of the elements described in connection with FIGS. 1-3.

In 502, a VM configuration is accessed. For example, an administrator module (e.g., administrator module 114) (and/or agent(s)) can access a VM configuration (e.g., VM configuration 112). It is noted that the administrator module can be distributed across (and/or executed by) several nodes of a single or several clusters, as desired. The VM configuration is associated with a VM that is to be hosted by a node. In one embodiment, the VM associated with the VM configuration is not yet hosted on any node of any cluster. In other words, the VM configuration may be received by a command for creating and/or hosting this VM. In another embodiment, this VM is already being hosted by a node on one of clusters in the system. In this case, a command may be received for provisioning the VM from one node to another node (on the same or different cluster).

In 504, a cluster configuration is accessed. For example, the administrator module (and/or agent(s)) can access a cluster configuration (e.g., cluster configuration 110). The cluster configuration can be stored on one or more nodes of the respective cluster and/or be stored outside of this cluster. In one embodiment, the cluster configuration can include node configuration for node(s) in that respective cluster. In one embodiment, cluster configuration can include both information about resources for node(s) in the cluster, as well as operational element(s) in the cluster. In one embodiment, when accessing the cluster configuration, the administrator module can determine the current operational characteristics of nodes in the cluster.

In 506, the VM configuration and the cluster configuration are compared. For example, the administrator module (and/or agent(s)) can compare VM configuration 112 and cluster configuration 110. The administrator module can determine whether the additional requirements match the operational elements of the nodes for the cluster. It is noted that steps 504 and/or 506 can be repeated for several clusters, as described with reference to FIG. 6.

In 508, the VM is provisioned at a node based on the comparison of element 506. For example, the administrator module (and/or agent(s)) can provision the VM for hosting at node 102A. In one embodiment, once this VM is hosted at the node, the VM configuration associated with this node can be stored along with VM configurations for other VMs in this cluster (e.g., with VM configurations for VMs 108A-108C).

FIG. 6 is a flowchart 600 of a method for management and provisioning of virtual machines, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 600 is described with reference to variations of the elements described in connection with FIGS. 1-3. In one embodiment, the method of FIG. 6 implements elements 504 and/or 506 of FIG. 5.

In 602, a cluster configuration of another cluster is accessed. For example, the administrator module (and/or agent(s)) can access one or more cluster configurations of clusters other than cluster 100. The cluster configuration can include node configuration for node(s) in that respective cluster, including both information about resources for node(s) in the cluster, as well as operational element(s) in the cluster.

In 604, the VM configuration and the cluster configuration are compared. For example, the administrator module (and/or agent(s)) can compare VM configuration 112 and cluster configuration for several clusters. The administrator module can determine whether the additional requirements match the operational elements of the nodes for each respective cluster.

In 606, a cluster is selected from the various clusters accessed by the administrator module. For example, based on the comparison(s) of step 604, the administrator module (and/or agent(s)) can determine which cluster matches with the additional requirements specified by the VM configuration. The administrator module can use various techniques for selecting the best matching cluster. In one embodiment, the administrator module can assign weights to various resource requirements and/or additional requirements. Depending on such weighting, different clusters may be selected. For example, if data protection is heavily weighted, then cluster(s) having nodes with sophisticated data protection mechanisms are likely to be selected. In another embodiment, the n-ary tree technique described below can be used.

In 608, a node is determined from the selected cluster. For example, once the administrator module (and/or agent(s)) determines a cluster for hosting the VM, a node can be determined in this selected cluster for hosting the VM. The administrator module can access node configurations for nodes in the selected cluster when making this determination. Various techniques can be used to select the node from the cluster, including using the node configurations to determine which node matches the VM configuration of the VM to be hosted. Once the node is determined, the administrator module can facilitate in hosting the VM on the determined node.

FIG. 7 is a block diagram illustrating a cluster 700 that includes a collection of nodes and storage. Cluster, e.g., cluster 700, includes several nodes, e.g., nodes 702A, 702B, and 703C. Each node can communicate with storage, e.g., storage 704, using a network, e.g., network 706. Although only three nodes 702A-702C are shown, cluster 700 may include a different number of nodes. Each such node can implement one or more virtual machines, e.g., virtual machines 708A-708D. In some embodiments, each node may implement virtual machines using hypervisor technology, although other designs are contemplated. Furthermore, some nodes can also implement an agent, e.g., agents 710A and 710B.

In one embodiment, node(s) in the cluster include cluster configuration, e.g., cluster configuration 712. Cluster configuration can include configuration information for the cluster and/or configuration information for node(s). For example, cluster configuration 712 can include configuration information 712A for node A 702A and configuration information 712B for node B 702B. It is noted that while FIG. 7 shows a single node (node C 702C) supporting such cluster configuration, which is done for illustrative purposes only. Such a cluster configuration 712 can be implemented, accessed, and/or stored anywhere in cluster 700. For example, cluster configuration 710 can be distributed among nodes 702A and 702B of cluster 700, and/or storage 704. Cluster configuration can also be stored outside cluster 700, such as at a central repository, and be accessed via network 706, as desired. In one embodiment, cluster configuration and/or VM configuration can be stored in a database. Such database can store cluster configuration and/or VM configuration for several clusters.

VM configuration, such as VM configuration 714, includes resource requirement(s), and one or more additional requirement(s). It is noted that while FIG. 7 shows a single node (node C 702C) supporting such VM configuration, which is done for illustrative purposes only. Such VM configuration 714 can be supported, implemented, accessed, and/or stored anywhere in cluster 700. For example, VM configuration 714 can be distributed among nodes 702A and 702B of cluster 700, and/or storage 704. VM configuration can also be stored outside cluster 700, such as at a central repository, and be accessed via network 706, as desired. In one embodiment, the VM configuration is included in the VM's service level agreement (SLA). As shown, VM configuration 714 can include VM configurations 714A and 714B associated with VM 708A and 708B, respectively. Both of VM 708A and 708B are already being hosted by node 702A. VM configurations associated with VM 708C and/or 708D can be also stored by VM configuration 714, and/or can be stored elsewhere.

In one embodiment, administrator module 716 (and/or agent(s)) access virtual machine configuration 714 associated with a VM that is already being hosted. For example, administrator module 716 perform an analysis that such a VM is to be provisioned at a node at a cluster, as long as this node matches the requirements in the VM configuration associated with this VM. Administrator module 116 can access cluster configuration 110 of cluster 100. Administrator module 116 can then compare VM configuration 112 and cluster configuration 110. Administrator module 116 can also access a cluster configuration of another cluster. This example illustrates how the administrator node can access cluster configuration of several clusters. Thus, administrator module 116 (and/or agent(s)) can access cluster configuration (not shown) of other clusters. The administrator module can also be distributed among nodes of different clusters, as desired.

In one embodiment, the administration module and/or the agent(s) for the nodes determine operational indicator(s) of the nodes, e.g., nodes 702A and 702B. The operational indicator(s) indicate operation characteristics of each respective node. These operational indicator(s) can include availability, data protection, and/or security requirements, among others. Operational indicator(s) can be dynamic, i.e., they can change over time. An agent on each node (e.g., agent 710A on node 702A) can determine operational indicator(s) for node 702A. In one embodiment, each node can use a separate agent. In another embodiment, agent(s) can be associated with several nodes in a single cluster, as desired.

The administrator module (and/or agent(s)) can compare the operational elements (i.e., of the respective VM configuration) and the operational indicators of the respective node. Such a comparison can be performed to determine whether the node is still providing the operational characteristics for the VM that were specified prior to hosting this VM on the node. The administration module (and/or agent(s)) can thus determine whether a VM is operating within its operating characteristics (as specified by its VM configuration, e.g., in an SLA). This comparison can be performed for several VMs of cluster 700.

FIG. 8 is a block diagram illustrating an administrator module accessing cluster configuration 804 and VM configuration 820, according to one embodiment. As shown, administrator module 802 includes a configuration module 806, a provisioning module 808, a comparison module 810, a determination module 812, a selection module 814, an operational indicator module 816, and an alert module 818. It is noted that in some embodiments, the various modules of administrator module 802 may be combined or further divided, and are depicted in FIG. 8 as such, solely for purposes of illustration. Thus, administrator module 802 may include fewer, or additional modules, as desired. Furthermore, in some embodiments, one or more of these modules may be combined. For example, comparison module 810 and determination module 812 can be combined into one module. Still further, various modules of administrator module 802 may be may be implemented as a single software and/or hardware module, as desired. Administrator module 802 can be an implementation of administrator module 114 of FIG. 1 and/or administration module 716 of FIG. 7. In one embodiment, various modules of administrator module 802 may operate analogously to that of administrator module 202 of FIG. 2A. In one embodiment, agent(s) can implement some, or all, of functionality of the administrator module.

Comparison module 810 is operable to compare VM configuration of a VM and node configuration associated with the node that is hosting this VM. For example, comparison module 810 can access VM A configuration 820A associated with a VM (e.g., VM 708A) that is hosted by a node (e.g., node 702A). Comparison module 810 can compare this VM A configuration 820A and the configuration for this node (i.e., node 702A). In one embodiment, comparison module 810 may access resources and/or operational elements of this node. Comparison module 810 can determine whether the additional requirements (of VM configuration) match the operational elements of the node that is hosting the respective VM.

Operational indicator module 816 is configured to determine operational indicator(s) of node(s) included in a cluster (e.g., nodes 702A and 702B of cluster 700). Operational indicator module 816 can communicate with agent(s) on respective node(s). For example, agent(s) can be executed in order to determine various operational characteristics of a node. The agent(s) can then send the operational characteristics to the operational indicator module 816, which can then generate the operational indicators using the received operational characteristics. In one embodiment, the agent(s) can generate the operational indicators, and then send the operational indicators to the operational indicator module 816.

Determination module 812 is configured to determine a deviation by performing an analysis, and determine whether the deviation is within a range. Alert module 818 is configured to generate an alert if this deviation is outside a range. In one embodiment, the range is predetermined prior to this deviation determination. In another embodiment, the range is dynamically determined, such as when determining the operational indicator(s) of the node. Administrator module 802 can access cluster configuration 804 and/or VM configuration 820 using a connection 822, which can be a memory bus, software API/function calls, notifications, data messaging, and/or a network, etc., depending on implementation.

FIG. 9 is a block diagram 900 of a cluster configuration 902, such as a cluster configuration described in previous Figures. Cluster configuration 902 can include cluster A configuration 902A for a first cluster (e.g., cluster 700) and cluster B configuration 902B for another cluster (not shown). Cluster configuration 902 can be stored in a repository, in a database, or be distributed among various clusters, or storage elements, as desired.

FIG. 10 is a block diagram 1000 of a cluster configuration 1002, such as cluster configuration described in previous Figs. Cluster configuration 1002 can include configuration information for nodes of a given cluster, i.e., by using node configuration 1004A-1004N. Cluster configuration 1002 can also include operational indicators 1006A-1006N. It is noted that operational indicators 1006A-1006N can be determined dynamically for a cluster and/or node of that cluster. For example, some operational indicators can be associated with the cluster, whereas other operational indicators can be associated with nodes of that cluster.

FIG. 11 is a block diagram illustrating a notification system 1100 that includes a notification infrastructure and notification modules, according to one embodiment. The notification system can be used to communicate notifications and/or responses between VMs, nodes, agents, and/or administration module(s). The notification system includes node notification modules 1102(1)-1102(N), cluster notification modules 1104(1)-1104(M), a notification broadcast module 1106, and a notification infrastructure 1108.

Node notification modules 1102 are associated with nodes of one or more clusters. Cluster notification modules 1104 are associated with clusters. Notification infrastructure 1108 facilitates sending and receiving of notifications (and responses) between notification modules 1102 and 1104. In one embodiment, node notification module 1102 sends notifications, such as notifications indicating that an operation of a node has changed. For example, an operational characteristic of a node may be modified, from having one type of data protection to another type of data protection. Such change can be detected, for example, by an agent (e.g., an agent executing on that node). As a result of this change being detected, a node notification module associated with that node can send a notification informing recipient(s) of this change. In some embodiments, the nodes are monitored for changes. In one embodiment, agent(s) can include and/or implement a node notification and/or cluster notification module(s).

Notification broadcast module 1106 is optional, and may be used in some embodiments. For example, a notification module 1102 and/or 1104 can send a notification to notification broadcast module 1106. Notification broadcast module 1106, in response to receiving such a notification from notification module 1102, can sent additional notifications (e.g., substantially similar notifications) to other notification modules 1102 and/or 1104. These notification modules 1102 and/or 1104, upon receiving a notification of change, can communicate (a notification, e.g., that this change occurred) to agent(s) and/or administrator module(s). The agent(s) and/or administrator module(s), upon receiving this notification, can access VM configuration of a VM that is being hosted by a node associated with this notification (i.e., a node where the operational characteristic was modified). In some embodiments, prior to accessing the VM configuration, the agent(s) and/or administrator module(s) first determine VM(s) that are being hosted by such a node. The agent(s) and/or administrator module(s) can then determine whether one or more VMs are operating within the operating characteristics (e.g., as specified by the respective VM configuration).

FIG. 12 is a flowchart 1200 of a method for management and provisioning of virtual machines, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 1200 is described with reference to variations of the elements described in connection with FIGS. 7 and 11. It is noted that in some embodiments, various elements of the method of FIG. 12 (e.g., elements 1206-1210) are performed in response to receiving a notification that an operational characteristic of a node has changed. In other embodiments, various elements of the method of FIG. 12 (e.g., elements 1206-1210) are performed during a routine check of various nodes of a cluster to make sure that operational characteristics of a node have not deviated outside some range.

In 1202, a VM is hosted by a node. For example, VM 708D is provisioned and thus hosted by node 702B.

In 1204, a VM configuration is accessed. For example, an administrator module (e.g., administrator module 716) and/or any of agent(s) 710A-710B can access a VM configuration (e.g., VM configuration 112). It is noted that the administrator module can be distributed across (and/or executed by) several nodes of a single or several clusters, as desired. The VM configuration is associated with a VM being hosted by node.

In 1206, the operational indicators are determined. In one embodiment, the administrator module and/or agent(s) determine the current operational characteristics of nodes in the cluster. The operational indicator(s) indicate operation characteristics of each respective node. These operational indicator(s) can include availability, data protection, and/or security requirements, among others. For example, agent 710B on node 702B can determine operational indicator(s) for node 702B. In one embodiment, the administrator module and/or agent(s) can access a cluster configuration (e.g., cluster configuration 712). The cluster configuration can be stored on one or more nodes of the respective cluster and/or be stored outside of this cluster. In one embodiment, the cluster configuration includes node configuration for node(s) in that respective cluster. In one embodiment, cluster configuration can include both information about resources for node(s) of the cluster, as well as operational element(s) of the cluster, including operational indicators of the node.

In 1208, the VM configuration and operational indicators are compared. For example, the administrator module and/or agent(s) can compare VM configuration 714D and cluster configuration 712. The administrator module can determine whether the additional requirements match the operational elements of the nodes for the cluster.

In 1210, as action is performed based on the comparison of element 1208. For example, an alert may be generated if the comparison determines that the operational indicators on the node are outside of some range.

FIG. 13 is a flowchart 1300 of a method for management and provisioning of virtual machines, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 1300 is described with reference to variations of the elements described in connection with FIGS. 7 and 11. In one embodiment, the method of FIG. 13 implements element 1208 of FIG. 12.

In 1302, a deviation is determined by performing an analysis. For example, the administrator module and/or agent(s) can access operational indicator(s) that were determined in element 1206. The administrator module and/or agent(s) can analyze the operational indicator(s) and the VM configuration to determine a deviation.

In 1304, it is determined whether the deviation is within a range. For example, the administrator module and/or agent(s) can determine whether the deviation is within a range. This range can be pre-determined prior to this analysis, or it may be dynamically determined.

In 1306, if it is determined that the deviation is within a range, it is indicated that the node is conforming to the VM configuration. In 1308, if it is determined that the deviation is outside the range, it is indicated that the node is not conforming to the VM configuration. For example, the administrator module and/or agent(s) can make this indication based on the determination of element 1304.

FIG. 14 is a block diagram illustrating a couple of clusters, each including a collection of nodes and storage. A first cluster 1400A includes several nodes, e.g., nodes 1402A and 1402B. Each node of first cluster 1400A can communicate with storage, e.g., storage 1404A, using a network, e.g., network 1406A. Although only two nodes 1402A-1402B are shown, cluster 1400A may include a different number of nodes. node(s) can implement one or more virtual machines, e.g., virtual machines 1408A-1408B. Some nodes can also implement an agent, e.g., agents 1410A and 1410B. Similarly, a second cluster 1400B includes nodes 1402C and 1402D, virtual machines 1408C and 1408D, agent(s) 1410C and 1410D, and storage 1404B. Clusters 1400A and 1400B can communicate using a network 1414, which can be a wide area network (WAN), Internet, etc.

In one embodiment, the administration module and/or the agent(s) for the nodes can select a cluster from the clusters (e.g., clusters 1400A and 1400B) for hosting of a VM. In one embodiment, this selection can be determined as described with reference to the previous Figs. In another embodiment, the administration module and/or the agent(s) for the nodes can generate a cluster rank for each cluster. The cluster rank can indicate a likelihood of at least one of nodes of each cluster to host the VM. This cluster rank can be generated based on the VM configuration. In one implementation, the cluster information can store the cluster rank for each cluster. Selection of the cluster is based on the respective rating of each of the plurality of clusters.

In one embodiment, the generation of each cluster rank is performed based on node ranks of at least some of nodes for that cluster. For example, node ranks of nodes 1402A and 1402B can be used to calculate the cluster rank of cluster 1400A. Similarly, node ranks of nodes 1402C and 1402D can be used to calculate the cluster rank of cluster 1404B. In one embodiment, an agent of each of these nodes can calculate this node rank. For example, agent 1410A for node 1402 can calculate node rank for node 1402A. Agents 1410B-1410D can calculate node ranks for nodes 1402B-1402D. The node rank indicates how that node matches the resource requirement(s) (e.g., of VM configuration). In one embodiment, prior to generating the cluster rank, some of the node ranks can be filtered out based on the VM configuration. In one embodiment, the administrator module (not shown) and/or agent(s) can perform the generation of the cluster rank and/or node ranks by using an n-ary tree approach, as described below.

FIG. 15 illustrates an n-ary tree, such as may be used by the administrator module and/or agent(s). The n-ary tree 1500 can contain multiple levels that contain multiple tree nodes. The levels can include a root node 1502A, a first leaf level (tree nodes 1502B, 1502E, and 1502I), and a second leaf level (tree nodes 1502C, 1502D, 1502F, 1502G, 1502H, 1502J, 1502K, and 1502L). In one embodiment, the first leaf nodes represent at least some of the clusters, e.g., tree node 1502B represents cluster 1400A and tree node 1502E represents cluster 1400B. In one embodiment, the second leaf nodes represent at least some of the nodes of each cluster, e.g., tree node 1502C represents node 1402A, tree node 1502D represents node 1402B, etc. It is noted that use of additional tree node levels is contemplated, e.g., FIG. 15 is only shown as an example implementation.

In one embodiment, nodes represented by some of the first tree nodes calculate their own respective node rank. Furthermore, nodes associated with clusters represented by some of the second tree nodes can calculate their respective cluster rank based on the node ranks of its leaf (i.e., associated lower-level) tree nodes. Thus, a tree node 1502B associated with cluster rank for cluster 1400A can calculate the cluster rank based on node ranks of lower level tree nodes 1502C and 1502D. It is noted that with reference to FIG. 14, one or more of the agents 1410A and 1410B can implement the computation associated with performing calculations for the cluster level tree nodes.

The n-ary tree is used for the distribution of work for finding more suitable clusters in the data center that can meet the virtual machine's VM configuration requirement(s) (e.g., SLA requirement(s)). In the n-ary tree, each parent (e.g., a root node for a sub-tree) distributes work to its children (e.g., leaf nodes of that subtree). Each parent node can also aggregate response from its children to pass on to its parent. The root of the n-ary tree receives response from all clusters. In one embodiment, the root tree node can aggregate final list of suitable clusters in the system (e.g., a data center).

In one embodiment, a node that is represented by each tree node performs a node ranking based on the VM configuration (e.g., the SLA requirement for the VM). The N-ary tree is built such that the lowest level of the N-ary tree is built from the sub-trees for each cluster. As a result, the root of each cluster's sub-tree will have SLA match ranking information for all the hosts in the cluster when it receives response from all its children. The root of the cluster's sub-tree can find the cluster's overall match for each of the SLA requirement by aggregating the SLA match for all the hosts belonging to the cluster. This distribution of analysis and rank generation among leaf tree nodes is efficient, as it localizes the cluster level decision making within the cluster itself.

In one embodiment, a next (higher) level of the N-ary tree is generated by grouping the clusters belonging to the same subnet together. Grouping at the subnet level can reduce multiple hop network traffic to pass the ranks for each cluster's match for each of the SLA requirement. Also, the n-ary tree can be built such that any node can have max N children. In one embodiment, the choice of N can be made based on the optimal fan-out of the communication mechanism used for the distribution across nodes.

FIG. 16 is a flowchart 1600 of a method for management and provisioning of virtual machines, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 1600 is described with reference to variations of the elements described in connection with FIGS. 14 and 15.

In element 1602, a cluster rank is generated for several clusters. For example, one or more agent(s) 1410A-1410D can generate a cluster rank for clusters 1400A and 1400B.

In element 1604, a cluster is selected from the clusters. For example, one or more agent(s) 1410A-1410D can select a cluster for hosting a node. This selection can be based on the cluster ranks, such as generated in element 1602.

In element 1606, a virtual machine is provisioned on a node of the selected cluster. In one implementation, a node can be selected from the selected cluster. For example, if element 1604 selects cluster 1400A, a new virtual machine (VM) can be provisioned on node 1402B once this node is selected from this cluster. Alternatively, a VM can be moved from another cluster to cluster 1400A, if for example, a node that was hosting that VM can no longer provision that VM according to that VM's configuration (e.g., operating requirements listed in that VM's SLA).

FIG. 17 is a flowchart 1700 of a method for management and provisioning of virtual machines, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 1700 is described with reference to variations of the elements described in connection with FIGS. 7 and 11. In one embodiment, the method of FIG. 17 implements at least a portion of element 1602 of FIG. 16. In one embodiment, the method of FIG. 17 is implemented when calculating node rankings of each node. In one implementation, the method of FIG. 17 can be implemented when generating an n-ary tree.

In element 1702, one or more nodes is filtered out. As noted, when node rankings are calculated for each node, some of the nodes may be filtered out before the n-ary tree is build, e.g., to save computational bandwidth. Such nodes may be filtered out if the calculated node rank is lower than some threshold and/or a range. In one embodiment, a certain lowest percentage of nodes (e.g., the bottom 10% of all nodes) are filtered out.

In element 1704, the n-ary tree can be build. It is noted that in some embodiments, the n-ary tree can be build without executing element 1702.

FIG. 18 is a flowchart 1800 of a method for generating of a n-ary tree, according to one embodiment. As will be appreciated in light of the present disclosure, this method may be modified in order to derive alternative embodiments. Also, the steps in this embodiment are shown in sequential order. However, certain steps may occur in a different order than shown, certain steps may be performed concurrently, certain steps may be combined with other steps, and certain steps may be absent in another embodiment. Method 1800 is described with reference to variations of the elements described in connection with FIGS. 7 and 11. In one embodiment, the method of FIG. 18 implements at least a portion of element 1602 of FIG. 16 and/or element 1704 of FIG. 17.

In element 1802, cells may be split into multiple groups. When generating an n-ary tree, each node (e.g., in the clusters being considered) can be represented by a cell.

In element 1804, one or more sub-trees may be built from the multiple groups. The second level tree nodes can be added to be a sub-root node for each sub-tree. Each such sub-root node, e.g., node 1502B, 1502E, and 1502I, can represent a cluster. For example, with reference to FIG. 15, a first sub-tree can include nodes 1502B-1502D, a second sub-tree can include nodes 1502E-1502H, and a third sub-tree can include nodes 1502I-1502L. Thus, the first sub-tree can include nodes for the first cluster (e.g., 1400A), the second sub-tree can include nodes for the second cluster (e.g., 1400B), etc. In other embodiments, the tree nodes in the sub-trees can be grouped by subnets, or geographical proximity of nodes, etc.

In element 1806, a root node may be assigned for the sub-trees. Such a root node can connect all of the sub-trees together. For example, referring to, e.g., FIG. 15, node 1502 is the root node for n-ary tree 1500.

In element 1808, each cell (e.g., each tree node) in the lower tree level can calculate its own node rank. For example, the tree nodes in the lower tree level represent nodes. Agent(s) associated with each such node (e.g., agent 410A associated with node 1402A that is represented by tree node 1502C) can calculate its own node rank. In one embodiment, once the node ranks are calculated, some tree nodes are filtered out (e.g., if the node rank is below a certain threshold and/or is outside a certain range) before proceeding to the next element in method 1800.

In one embodiment, VM configuration requirements is communicated to the root node of the N-ary tree. Every non-leaf node in the N-ary tree can divide the work among its children and find its own available capacity and ranking. Each node (that is represented by each tree node) can calculate its node rank by running an algorithm. This algorithm can consider i) virtual machine's requirements (CPU, Memory, availability, data protection, storage, security, etc.), ii) the node's estimated available capacity for each resource; and iii) and the data center (e.g., save power, high performance), cluster, host & virtual machine (e.g. guaranteed resources, affinity, non-affinity, etc) policies. In one implementation the estimated available capacity is calculated using analytical techniques such as self-learning or forecasting on resource usage & static policies.

In element 1810, each cell (e.g., each tree node) in the second tree level calculates its own cluster rank. For example, the tree nodes in the lower tree level represent nodes. Agent(s) associated with each such node (e.g., agent 410A associated with node 1402A that is represented by tree node 1502C) can calculate its own node rank. In one embodiment, agent(s) of a cluster can also implement any computation for the second level tree node(s). For example, agent 1410A can also implement the computation(s) for element 1810.

Elements of network architecture can be implemented using different computer systems and networks. An example of one such network environment is described below with reference to FIG. 19. FIG. 19 is a simplified block diagram illustrating a network architecture 1900 in which one or more clients are provided with access to a server via various network connections. As depicted in FIG. 19, clients 1902(1)-(N) are coupled to a network 1910, and so are able to access a server 1906 (which can be used to implement node(s) of FIGS. 1, 7, 14 and/or notification controller) via network 1910. Other servers (not shown) can be used instead to implement system(s) node(s) of FIGS. 1, 7, 14 and/or notification controller). A client can be implemented using, for example, a desktop computer, a laptop computer, a workstation, a server, a cell phone, a smart phone, a network-enabled personal digital assistant (PDA), or the like. An example of network 1910, which can be used by clients 1902(1)-(N) to access server 1906, is the Internet. Alternatively, access to server 1906 can be provided by a local area network (LAN) utilizing Ethernet, IEEE 802.11x, or some other communications protocol. As will be appreciated, server 1906 can be accessed by clients coupled directly thereto (not shown).

As also depicted on FIG. 19, server 1906 is coupled to a server storage device 1908, which includes a data volume such as cluster shared volume. Server storage device 1908 can be implemented as a single storage device or a collection of storage devices. Server storage device 1908 can also be implemented as a storage area network, which couples remote storage devices to a server (e.g., server 1906), such that the remote storage devices appear as locally-attached storage devices to the server's OS, for example.

In light of the present disclosure, those of skill in the art will appreciate that server storage device 1908 can be implemented by any type of computer-readable storage medium, including, but not limited to, internal or external hard disk drives (HDD), optical drives (e.g., CD-R, CD-RW, DVD-R, DVD-RW, and the like), flash memory drives (e.g., USB memory sticks and the like), tape drives and the like. Alternatively, those of skill in the art will also appreciate that, in light of the present disclosure, network architecture 1900 can include other components such as routers, firewalls and the like that are not germane to the discussion of the present network and will not be discussed further herein. Those of skill in the art will also appreciate that other configurations are possible. For example, clients 1902(1)-(N) can be directly coupled to server storage device 1908 without the user of a server or Internet; server 1906 can be used to implement both the clients and the server; network architecture 1900 can be implemented without the use of clients 1902(1)-(N); and so on.

As an example implementation of network architecture 1900, server 1906, services requests to data generated by clients 1902(1)-(N) to data stored in server storage device 1908. Any of the functionality of the nodes, agents, and/or administration modules can be implemented using one of the other servers in the manner illustrated by FIGS. 1, 7, 14.

FIG. 20 depicts a block diagram of a computer system 2010 suitable for implementing the present disclosure. Computer system 2010 may be illustrative of various computer systems in the networked system of FIGS. 1, 7, 14, such as node(s) and/or notification controller, among others. Computer system 2010 includes a bus 2012 which interconnects major subsystems of computer system 2010, such as a central processor 2014, a system memory 2017 (typically RAM, but which may also include ROM, flash RAM, or the like), an input/output controller 2018, an external audio device, such as a speaker system 2020 via an audio output interface 2022, an external device, such as a display screen 2024 via display adapter 2026, serial ports 2028 and 2030, a keyboard 2032 (interfaced with a keyboard controller 2033), a storage interface 2034, a floppy disk drive 2037 operative to receive a floppy disk 2038, a host bus adapter (HBA) interface card 2035A operative to connect with a Fibre Channel network 2090, a host bus adapter (HBA) interface card 2035B operative to connect to a SCSI bus 2039, and an optical disk drive 2040 operative to receive an optical disk 2042. Also included are a mouse 2046 (or other point-and-click device, coupled to bus 2012 via serial port 2028), a modem 2047 (coupled to bus 2012 via serial port 2030), and a network interface 2048 (coupled directly to bus 2012).

Bus 2012 allows data communication between central processor 2014 and system memory 2017, which may include read-only memory (ROM) or flash memory (neither shown), and random access memory (RAM) (not shown), as previously noted. The RAM is generally the main memory into which the operating system and application programs are loaded. The ROM or flash memory can contain, among other code, the Basic Input-Output system (BIOS) which controls basic hardware operation such as the interaction with peripheral components. Applications resident with computer system 2010 are generally stored on and accessed via a computer readable medium, such as a hard disk drive (e.g., fixed disk 2044), an optical drive (e.g., optical drive 2040), a floppy disk unit 2037, or other storage medium. Additionally, applications can be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via network modem 2047 or interface 2048.

Storage interface 2034, as with the other storage interfaces of computer system 2010, can connect to a standard computer readable medium for storage and/or retrieval of information, such as a fixed disk drive 2044. Fixed disk drive 2044 may be a part of computer system 2010 or may be separate and accessed through other interface systems. Modem 2047 may provide a direct connection to a remote server via a telephone link or to the Internet via an internet service provider (ISP). Network interface 2048 may provide a direct connection to a remote server via a direct network link to the Internet via a POP (point of presence). Network interface 2048 may provide such connection using wireless techniques, including digital cellular telephone connection, Cellular Digital Packet Data (CDPD) connection, digital satellite data connection or the like.

Many other devices or subsystems (not shown) may be connected in a similar manner (e.g., document scanners, digital cameras and so on). Conversely, all of the devices shown in FIG. 20 need not be present to practice the present disclosure. The devices and subsystems can be interconnected in different ways from that shown in FIG. 20. The operation of a computer system such as that shown in FIG. 20 is readily known in the art and is not discussed in detail in this application. Code for the automatically performing operations on such applications based on their dependencies on other applications (such as described above with reference to the methods of FIGS. 5, 6, 12, 13, and 16-18), etc., to implement the present disclosure can be stored in computer-readable storage media such as one or more of system memory 2017, fixed disk 2044, optical disk 2042, or floppy disk 2038. Memory 2020 is also used for storing temporary variables or other intermediate information during the execution of instructions by the processor 2010. The operating system provided on computer system 2010 may be MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, Linux®, or another known operating system.

Moreover, regarding the signals described herein, those skilled in the art will recognize that a signal can be directly transmitted from a first block to a second block, or a signal can be modified (e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered, or otherwise modified) between the blocks. Although the signals of the above described embodiment are characterized as transmitted from one block to the next, other embodiments of the present disclosure may include modified signals in place of such directly transmitted signals as long as the informational and/or functional aspect of the signal is transmitted between blocks. To some extent, a signal input at a second block can be conceptualized as a second signal derived from a first signal output from a first block due to physical limitations of the circuitry involved (e.g., there will inevitably be some attenuation and delay). Therefore, as used herein, a second signal derived from a first signal includes the first signal or any modifications to the first signal, whether due to circuit limitations or due to passage through other circuit elements which do not change the informational and/or final functional aspect of the first signal.

Although the present invention has been described in connection with several embodiments, the invention is not intended to be limited to the specific forms set forth herein. On the contrary, it is intended to cover such alternatives, modifications, and equivalents as can be reasonably included within the scope of the invention as defined by the appended claims.

Aspects of the disclosure are also further discussed in the following paragraphs. 

What is claimed is:
 1. A method comprising: generating a respective cluster rank for each of a plurality of clusters, wherein each of the clusters comprises a plurality of potential nodes, each of a plurality of second tree nodes calculates a respective node rank based, at least in part, on a virtual machine (VM) configuration, wherein an n-ary tree comprises at least two leaf levels, a second leaf level of the n-ary tree comprises the plurality of second tree nodes, and each of the second tree nodes represents one of the potential nodes, and each of a plurality of first tree nodes calculates the respective cluster rank based, at least in part, on an aggregate rank of the respective node ranks of the potential nodes in each cluster, wherein a first leaf level of the n-ary tree comprises the plurality of first tree nodes, and each of the first tree nodes represents one of the clusters; selecting a selected cluster from the plurality of clusters, wherein the plurality of potential nodes are configured to host one or more virtual machines, each of the plurality of clusters comprises respective cluster information, the respective cluster information comprises information for the plurality of potential nodes of the plurality of clusters, a VM is to be hosted by one of the plurality of potential nodes, a VM configuration of the VM comprises one or more resource requirements, the one or more resource requirements indicate one or more resources needed in a potential node for hosting the VM, and the selecting is based on the cluster rank of each cluster, the respective cluster information, and the VM configuration; and provisioning the VM by a selected node, wherein the selected cluster comprises the selected node.
 2. The method of claim 1, wherein: the respective cluster information comprises the respective cluster rank for a respective cluster, the respective cluster rank of each of the clusters indicates a likelihood of at least one of the respective plurality of potential nodes of the respective cluster to host the VM, and the respective cluster rank of each of the clusters is generated based on the VM configuration.
 3. The method of claim 2, wherein the generating the respective cluster rank of each of the plurality of clusters is performed based on the respective node ranks of at least some of the plurality of potential nodes.
 4. The method of claim 3, wherein each of the respective node ranks indicates how well the one or more potential nodes in each of the plurality of clusters matches the one or more resource requirements.
 5. The method of claim 3, further comprising: prior to generating the respective cluster rank, filtering out one or more of the respective node ranks based on the VM configuration.
 6. The method of claim 3, further comprising: prior to generating the respective cluster rank, generating the n-ary tree, wherein the plurality of tree nodes are arranged in a plurality of levels, the plurality of levels comprise a root level, and at least the first leaf level and the second leaf level, and the root level comprises a root tree node.
 7. The method of claim 1, wherein the VM configuration further comprises one or more additional requirements, and the one or more additional requirements indicate one or more operational elements needed in a node for hosting the VM.
 8. The method of claim 1, wherein the selecting is further based on one or more operational indicators, wherein the operational indicator(s) indicates operation characteristics of one or more of at least one of the plurality of potential nodes, or at least one of the plurality of clusters.
 9. A system comprising: one or more processors, a VM configuration, wherein the VM configuration comprises one or more resource requirements, the one or more resource requirements indicate one or more resources needed in a node for hosting a VM a cluster of a plurality of clusters comprises the node, each of the plurality of clusters comprises a plurality of potential nodes, and the plurality of potential nodes are configured to host one or more virtual machines (VMs); and a plurality of agents, wherein at least one of the potential nodes comprises one of the plurality of agents, at least one of the plurality of agents is configured to select one of the clusters as a selected cluster, the selected cluster is based, at least in part, on a respective cluster rank associated with the cluster, wherein each of a plurality of second tree nodes calculates a respective node rank based, at least in part, on the VM configuration, wherein an n-ary tree comprises at least two leaf levels, a second leaf level of the n-ary tree comprises the plurality of second tree nodes, and each of the second tree nodes represents one of the potential nodes, and each of a plurality of first tree nodes calculates the respective cluster rank based, at least in part, on an aggregate rank of the respective node ranks of the potential nodes in each cluster, wherein a first leaf level of the n-ary tree comprises the plurality of first tree nodes, and each of the first tree nodes represents one of the clusters; the selected cluster is selected based on respective cluster information and the VM configuration, a selected node in the selected cluster is configured to host the VM, and the at least one of the plurality of agents is configured to be executed using the one or more processors.
 10. The system of claim 9, wherein at least one of the plurality of agents is configured to generate the respective cluster rank for at least one of the plurality of clusters, wherein the respective cluster information comprises the respective cluster rank for the respective cluster, the respective cluster rank indicates a likelihood of at least one of the respective plurality of potential nodes of the respective cluster be capable of hosting the VM, and the respective cluster rank is generated based on the VM configuration.
 11. The system of claim 9, wherein the plurality of agents are configured to prior to generation of the respective cluster rank, generate the n-ary tree, wherein the plurality of tree nodes are arranged in a plurality of levels, the plurality of levels comprise a root level, and at least the first leaf level and the second leaf level, and the root level comprises a root tree node.
 12. The system of claim 9, wherein the VM configuration further comprises one or more additional requirements, and the one or more additional requirements indicate one or more operational elements needed in a potential node for hosting the VM.
 13. The system of claim 9, wherein the selection is further based on one or more operational indicators, the operational indicator(s) indicates operation characteristics of one or more of at least one of the plurality of potential nodes, or at least one of the plurality of clusters.
 14. A computer program product comprising: a non-transitory computer storage media, wherein a plurality of instructions are encoded in the non-transitory computer storage media, a plurality of instructions, comprising a first set of instructions, executable on a computer system, configured to generate a respective cluster rank for each of a plurality of clusters, wherein each of the clusters comprises a plurality of potential nodes, each of a plurality of second tree nodes calculates a respective node rank based, at least in part, on a virtual machine (VM) configuration, wherein  an n-ary tree comprises at least two leaf levels,  a second leaf level of the n-ary tree comprises the plurality of second tree nodes, and  each of the second tree nodes represents one of the potential nodes, and each of a plurality of first tree nodes calculates the respective cluster rank based, at least in part, on an aggregate rank of the respective node ranks of the potential nodes in each cluster, wherein  a first leaf level of the n-ary tree comprises the plurality of first tree nodes, and  each of the first tree nodes represents one of the clusters; a second set of instructions, executable on the computer system, configured to select a selected cluster from the plurality of clusters, wherein the plurality of potential nodes are configured to host one or more virtual machines, a virtual machine (VM) is to be hosted by one of the plurality of potential nodes, each of the plurality of clusters comprises respective cluster information, the respective cluster information comprises information for the plurality of potential nodes of the plurality of clusters, a VM configuration comprises  one or more resource requirements, the one or more resource requirements indicate one or more resources needed in a potential node for hosting the VM, and the selection is based on the respective cluster information and the VM configuration; and a third set of instructions, executable on the computer system, configured to provision the VM on a selected node, wherein the selected cluster comprises the selected node.
 15. The computer program product of claim 14, wherein the first set of instructions is further configured to: prior to selecting the selected cluster, generate the respective cluster rank of at least some of the plurality of clusters, wherein the respective cluster information comprises the respective cluster rank for the respective cluster, the respective cluster rank indicates a likelihood of at least one of the respective plurality of nodes for the respective cluster to host the VM, and the respective cluster rank is generated based on the VM configuration.
 16. The computer program product of claim 15, wherein the generation of the respective cluster rank is performed based on the respective node ranks of at least some of the plurality of potential nodes.
 17. The computer program product of claim 16, wherein the instructions further comprise: a fourth set of instructions, executable on the computer system, configured to prior to the selecting, calculate the respective node rank for the at least some of the plurality of potential nodes, wherein the respective node rank indicates how well the one or more potential nodes in each of the plurality of clusters match the one or more resource requirements.
 18. The computer program product of claim 16, wherein the instructions further comprise: a fourth set of instructions, executable on the computer system, configured to prior to the generation of the respective cluster rank, generate the n-ary tree, wherein the plurality of tree nodes are arranged in a plurality of levels, the plurality of levels comprise a root level, and at least the first leaf level and the second leaf level, and the root level comprises a root tree node. 